Refactors context passing #5623
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What's the problem this PR addresses?
Passing the context to the CLI instance was impractical, as it required to know exactly what was the context that the commands expect. I think there's something to improve here in Clipanion itself (perhaps so that the context can be defined when instantiating the CLI, not running the first command), but that's for a separate time.
How did you fix it?
I made
getCliBaseadd adefaultContextfield to the CLI instance. I considered returning them as separate fields, but wasn't sure it'd be worth the hassle of conveying two different values. Might revisit in a follow-up PR.Checklist